Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it!) and we'll verify it.

What to do if you already signed the CLA

Individual signers

• It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

• Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
• The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
• The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

@googlebot I signed it!

CLAs look good, thanks!

ℹ️ Googlers: Go here for more info.

Hi @ngdevelop-tech, thank you for this fix. Could you update your commit message? That's the reason that one test is failing. Try something like:

docs: change lite-server baseDir path to output folder

That should help. Feel free to tag me when you're ready.

Hi @kapunahelewong, Thank you for the review, I have changed the commit message.
Please let me know if there are any changes required.

Thanks, for making that update, @ngdevelop-tech! It looks like those failures are flakes but rebasing might fix them. Once you've rebased, please let me know. 🌸

(edited for clarity)

Hi @kapunahelewong, I have rebased the branch, but circleci checks doesn't get triggered and it is still showing errors and failing. Please let me know what changes I need to do further to fix this.
Please help.

Ah, thanks, @ngdevelop-tech. It's currently at 82 commits behind (surely this happened since you tagged me). Please pardon my delay in responding. Could you rebase again? 🙏🏼(We'd have to rebase to merge anyway).

If you amend that commit message by getting rid of the following highlighted parts and push up, it should retrigger the tests:

When you're ready please tag me - I'll be on the lookout for the notification. Thank you!

@ngdevelop-tech, you did it!! Well done!!! 🎉

Hi @kapunahelewong, I have followed the workflow you mentioned, now all checked are passed.
Thank you for your guidance. It helped me a lot to learn new things,

Caretaker, this is a docs only change. Please let me know if I can help in any way. Thanks!

Thank you @kapunahelewong ,
It was a great learning experience 🙂.

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}